home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-04
/
ov_all.zip
/
TI595.ASC
< prev
next >
Wrap
Text File
|
1991-09-11
|
4KB
|
133 lines
PRODUCT : ObjectVision NUMBER : 595
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 1/2
TITLE : ObjectVision, Paradox, and the DOS Share.exe Command
It is assumed that because Windows offers multi-tasking
capabilities, it is possible that the data could be in use by
more than one application. For this reason, issues which
ordinarily come up with network users may affect Windows users as
well:
ObjectVision requires the use of SHARE.EXE to link to Paradox
tables, because ObjectVision uses the Paradox Engine. The
Paradox Engine requires SHARE.EXE to be loaded to preserve data
integrity and prevent multiple applications from manipulating the
data structure at the same time.
SHARE.EXE should always be loaded from DOS prior to starting
Windows in order for it to work properly. Windows suggests in
the README.TXT that share be loaded for the general operation of
Windows.
On networks, the PARADOX.NET file is shared. Paradox users use
the same PARADOX.NET file for Paradox and ObjectVision. Paradox
users will want to refer to the Paradox Network Administrator's
Guide for more information about NUPDATE.EXE which is where the
shared PARADOX.NET file is specified for Paradox.
ObjectVision specifies a PARADOX.NET path through a utility
called PXENGCFG.EXE which allows you to configure your WIN.INI
(Windows Initialization file) easily. This utility is described
in Appendix D of the ObjectVision Reference Guide.
Since you will likely use PXENGCFG.EXE only a few times, it is
not automatically included in the ObjectVision Windows group
during installation. The utility is placed in the ObjectVision
installation directory and should be run from the Windows Program
Manager.
From the Program Manager use File | Run and type PXENGCFG
(include the complete path if ObjectVision is not in your path).
Using the PXENGCFG.EXE utility, give a User Name which is 14
characters or less. Set your PARADOX.NET path to the one shared
on the network by the other Paradox users, as specified in
nupdate.exe. Specify the network type, and set the Share Local
Tables with Others box to yes (make sure an "X" appears here).
This will enable standard Paradox locks on the tables in use.
PRODUCT : ObjectVision NUMBER : 595
VERSION : 1.0
OS : WIN
DATE : September 11, 1991 PAGE : 2/2
TITLE : ObjectVision, Paradox, and the DOS Share.exe Command
Locking the tables ensures greater data integrity since only one
application will be able to manipulate the data structure at
time, while still allowing multiple users to add, delete, or
modify data in the table. For more information about Paradox
lock files refer to the Paradox User's Guide, Chapter 2 "Using
Paradox on a Network".
In the event that a session with ObjectVision or Paradox is
terminated unexpectedly one or both application may have left
lock files (denoted by their .LCK extension) in the directory
which was current during the interrupted work session. These
files should be removed before the ObjectVision application is
loaded again, or ObjectVision will report that lock files were
found.